Jmafoster1/marie kondo - #402
Conversation
🦙 MegaLinter status:
|
| Descriptor | Linter | Files | Fixed | Errors | Elapsed time |
|---|---|---|---|---|---|
| black | 30 | 1 | 1.23s | ||
| ✅ PYTHON | pylint | 30 | 0 | 6.24s |
See detailed report in MegaLinter reports
|
OK, so looking at the For reference, instantiating a causal test case currently looks like this: In the new system, it'd look like this, which would be a lot cleaner: |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #402 +/- ##
==========================================
+ Coverage 98.18% 98.54% +0.36%
==========================================
Files 32 25 -7
Lines 1704 1514 -190
==========================================
- Hits 1673 1492 -181
+ Misses 31 22 -9
... and 3 files with indirect coverage changes Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
|
Update: Turns out removing |
… patsy formula in a clean and robust way!
jwhogg
left a comment
There was a problem hiding this comment.
looks good, pending that set change
Closes #398 #394 #392
This PR gets rid of a load of relic infrastructure classes that no longer spark joy. The result is a much more streamlined testing workflow. Notable removals include:
MetamorphicRelationclass, in favour of directly generating test cases from a causal DAGScenario,Variable, andBaseTestCaseclasses, in favour of expressing variables as strings, and modelling scenarios as pandas query strings.CubicSplineEstimatorclass, in favour of specifying cubic splines as formulas withLinearRegressionEstimator.It also adds a new command "evaluate" to evaluate a DAG with respect to a given dataset (with confidence intervals for the number of passing test cases calculated by resampling, similar to data adequacy).